Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0970

reference
36-tree-1
name
0970
tree-preservation-order

undefined

36-tpo-1
uprn
address-text
point
POINT (-0.979264 50.849909)
geometry
MULTIPOLYGON (((-0.979221 50.849905,-0.979223 50.849913,-0.979229 50.849920,-0.979238 50.849926,-0.979250 50.849930,-0.979263 50.849932,-0.979276 50.849931,-0.979288 50.849927,-0.979298 50.849921,-0.979304 50.849914,-0.979306 50.849905,-0.979304 50.849897,-0.979298 50.849889,-0.979289 50.849883,-0.979277 50.849879,-0.979264 50.849878,-0.979251 50.849879,-0.979239 50.849883,-0.979230 50.849889,-0.979223 50.849896,-0.979221 50.849905)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL